home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000299_news@columbia.edu _Sat Feb 22 00:44:23 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
5KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id AAA18057
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 22 Feb 1997 00:44:22 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id AAA06504
for kermit.misc@watsun; Sat, 22 Feb 1997 00:44:20 -0500 (EST)
Path: news.columbia.edu!panix!news.mathworks.com!cam-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!super.zippo.com!zdc!zippo!news
From: cksam@macau.ctm.net (SAM, Chi-Kin)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-Kermit via INT14h
Date: Sat, 22 Feb 1997 03:26:17 GMT
Organization: Tecnologia Electronica Hermes
Lines: 104
Message-ID: <5elp42$csr@lex.zippo.com>
References: <urvCz8Q0+/Xa092yn@aixrs1.hrz.uni-essen.de>
Reply-To: cksam@macau.ctm.net
NNTP-Posting-Host: c6line6.macau.ctm.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsreader: Forte Agent .99g/16.339
Xref: news.columbia.edu comp.protocols.kermit.misc:6638
On Wed, 19 Feb 1997 14:06:54 +0100,
sl0528@aixrs1.hrz.uni-essen.de (Thomas Pothmann) wrote:
>Hi,
>
>I'm hardly trying to get MS-Kermit screwed up running as telnet client
>via INT14h - but it doesn't still work at all! :-(
>
>I can't handle TCP/IP connection as it is described in msk315.doc for
>serveral reasons: 1. The terminal server, to which I connect to,
>strongly recommends a PAP login, so I can't dial in with Kermit
>because of missing Link Control Protocol. 2. At the moment I prefer
>using pppshare rather than etherppp, because the former seems to work
>more stable and reliable than the latter; pppshare is a Novell ODI
>driver for use over a PPP link and emulates a class 1 (ethernet)
>driver. 3. I generally like to use a class 1 driver, because most of
>my DOS clients call for one (and this way does WATTCP)
>
>So why not get things working from the back? I'm trying exactly this
>with the help from *tcpport.exe*, which I found in the WATTCP tool
>kit. Please see note below:
>
>---
>Using MS-KERMIT with Waterloo TCP
>
>You may wish to use a communication program such as KERMIT
>rather than TELNET. Waterloo TCP makes this very easy to do
>with its TCPPORT program.
>
>Start by creating a configuration file which tells your com
>program to use the BIOS ports rather than hardware. For my
>version of KERMIT, the config file looks like:
>
>C:\TNKERMIT\MSKERMIT.INI
>set baud 9600
>set port bios1
>[...] some cool stuff deleted
>---
>
>Now we can start a telnet session from a batch file *telnet.bat* like
>this one for example: tcpport %1 23 "c:\kermit"
>
>So I've made a minimal mskermit.ini the following items within:
>
>set term type vt320 ; Change this if desired.
>set port 2 ; Change if desired. If COM3 or 4, read KERMIT.BWR.
>set speed 57600 ; Change if desired.
>set flow RTS/CTS ; Change to RTS/CTS if modem is configured for this.
>set term bytesize 8 ; Change to 7/8 if desired.
>set term color 0 34 47 ; Terminal screen fore- and background colors.
>
>define wattcp -
> set port bios2, set speed 57600, set duplex full, -
> set local-echo off, set flow none, -
> set handshake none, set parity none
>
>And here's my batch file:
>tcpport %1 23 "kermit do wattcp, connect, stay"
>
>I really get a connect to my host with the configuration mentioned
>above but my terminal screen is full of garbage; when I terminate
>those failed telnet sessions, my PPP link is broken - when I ping the
>host, there are no responses anyway and I must hang up the modem. :-((
>
>What's going wrong there? Who can help me?
>
>Ciao, Thomas.
>
>BTW: Does anybody know, where to get rather recent WATTCP
>binaries from? I didn't found any on WATTCP's home ftp server but only
>the sources; I found some exe.files on the ftp server of Cologne
>University, they are dated as of Sep 1994.
>
>PS: Please don't mind my bad english ...
>
I am playing with MS-Kermit version 3.15 beta 18, I tested it
working with PPPshare fine.
I do not using INT14h. I just setup up and load PPPshare as
usual. Then I make the following changes in mskermit.ini /
mscustom.ini:
set port tcp nnn.nnn.nnn.nnn (the host I want to connect)
set tcp addr dhcp (my isp can provide dhcp or bootp)
then I can telnet to any hosts now.
My observation is that after load the PPP stack and set port
statement in the mskermit.ini / mscustom.ini which set port to a
physical port instead with set port tcp nnn.nnn.nnn or set port
tcp my.host.domain.mane will break down the ppp connection
immediately.
You may try to download and use the beta version as I do, the
accompany document mentioned procedures to use etherppp some
information concern set up MS-kermitalso applying to PPPshare.
Good luck.
...SAM
===========================================================================
SAM, Chi-Kin (Mr.) at Hermes Electronics Technology Co. in MACAU
Tel: +(853)963609 Fax: +(853)511456 PGP key: http://macau.ctm.net/~cksam
e-mail: cksam@macau.ctm.net Mailing-addr.: P.O.Box 831, Macau, South CHINA
===========================================================================